home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
EnigmA Amiga Run 1997 February
/
EnigmA AMIGA RUN 15 (1997)(G.R. Edizioni)(IT)[!][issue 1997-02][PLANET CD V].iso
/
enigma
/
earcd
/
editor
/
editor1
/
frxedv2a.lha
/
FrexxEd
/
bin
/
FPLdb.doc
< prev
next >
Wrap
Text File
|
1995-02-08
|
2KB
|
75 lines
FPLdb - FPL debugging tool
~~~~~~~~~~~~~~~~~~~~~~~~~~
LEGAL STUFF
~~~~~~~~~~~
FPLdb is free software; you may redistribute for non commercial purposes
only. FPLdb is actually a part of the FPL developer archive.
FPLdb is written with the intent of being a fully working program,
but there are no guarantees at all, only that it occupies disk space and
acutally has been working for me more than once. The author of this program
takes no responsibility at all if it proves defective in any way.
USAGE
~~~~~
FPLdb [W=Window/k] [H=Help/s]
Window - Specify a window string to use. Default is
"CON:0/0/640/200/FPLdb/AUTO/CLOSE/WAIT/INACTIVE", but I can warmly
recommend the use of KingCON and a window string similar to:
"KCON:0/0/560/200/FPL debug output/MINI"
Help - Displays a very short description text.
DESCRIPTION
~~~~~~~~~~~
FPLdb is a small and still not very developed little tool to improve FPL
debugging. It displays a window, in which trace information about running
FPL programs can be shown.
All FPL programs in the system that are run in debug-mode will get the
current executed line-number and position written to the window. This sounds
much more complicated than it is.
DEBUG-MODE
~~~~~~~~~~
Debug-mode means all programs in this and lower levels that run after
'debug(1);' has been used. When the program that called debug(1) ends, the
debug-mode is switched off again.
Default debug-mode can be switched on by altering the global info variable
in FrexxEd called 'fpl_debug'. By setting that to 1, all programs started
in FrexxEd will start in debug-mode and thus cause debug output.
EXIT
~~~~
Quit FPLdb by sending CTRL-C to it and then close the window.
EXAMPLE
~~~~~~~
To have a look how FPL interprets the loop written like:
int a;
for(a=0; a<10; a++)
a++;
we start the execution by calling the debug-function with 'debug(1);' like:
int a;
debug(1);
for(a=0; a<10; a++)
a++;
(we could also have done it by simply switched on 'fpl_debug' before the
execution)
FPLdb will then write some text in its window that looks similar to:
2 :int a;
3 :for(a=0; a<10; a++)
4 :a++;
4 :a++;
4 :a++;
4 :a++;
4 :a++;
which then of course shows the interpret-trace of the program.